Load/Register Failures

Load/Register Failures

If a registered module fails to load, unregister and reload it with ml, ld, or lboot -L to get a more detailed error message about the failure. The kernel will fail to load or register a module for any of the following reasons:

The major number specified either in the master file or by the ml command is already in use.
The object file is not compiled with the correct options.
The module is an "old style" driver, with either xxxdevflag set to D_OLD, or if no xxxdevflag exists in the driver.
If the object file is corrupted, it may cause "invalid JMPADDR" errors from the relocation code in the kernel.
The kernel did not resolve all of the module's symbols.
All major numbers are in use.
The switch table is full.
Required entry points for the particular type of module are not found in the loaded object file.